home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Internet
/
Collection of Internet.iso
/
infosrvr
/
dev
/
www_talk.930
/
000918_Nathan.Torkington@vuw.ac.nz _Tue Apr 20 00:10:28 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-01-24
|
1KB
Return-Path: <Nathan.Torkington@vuw.ac.nz>
Received: from dxmint.cern.ch by nxoc01.cern.ch (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0)
id AA11657; Tue, 20 Apr 93 00:10:28 MET DST
Received: from kauri.vuw.ac.nz by dxmint.cern.ch (5.65/DEC-Ultrix/4.3)
id AA20134; Tue, 20 Apr 1993 00:30:11 +0200
Received: by kauri.vuw.ac.nz id AA12133
(5.65c/IDA-1.4.4 for www-talk@info.cern.ch); Tue, 20 Apr 1993 10:30:05 +1200
Date: Tue, 20 Apr 1993 10:30:05 +1200
From: Nathan Torkington <Nathan.Torkington@vuw.ac.nz>
Message-Id: <199304192230.AA12133@kauri.vuw.ac.nz>
To: www-talk@nxoc01.cern.ch
Subject: Authentication
HTTP2 ideas:
-- authentication
Currently I'm going to fake this with document delivery
via e-mail, but I'd rather have *real* authentication.
Should the authentication scheme be build in, or should
it be left to clients and servers to guess?
-- tracking changes
I should be able to ping a document and get a unique
value back (cf md5 or snefru) to see whether it has
changed or not.
Nat.